System and method for offloading data in a communication system

ABSTRACT

A method is provided in one example embodiment and includes receiving a data packet transported on a backhaul link at a first network element; de-capsulating the data packet; identifying whether the data packet is an upstream data packet; identifying whether the data packet matches an internet protocol (IP) access control list (ACL) or a tunnel endpoint identifier; and offloading the data packet from the backhaul link. In more specific embodiment, the method can include identifying that the data packet does not match the IP ACL or the tunnel endpoint identifier; and communicating the data packet to a second network element. In other examples, the method can include identifying that the data packet is a downstream data packet; identifying a service to be performed for the data packet that cannot be performed at the first network element; and communicating the data packet to a second network element.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority under 35 U.S.C. §119(e)of U.S. Provisional Application Ser. No. 61/389,971, entitled “SYSTEMAND METHOD FOR PROVIDING TRAFFIC OFFLOAD FOR LOGICAL TUNNELS” filed Oct.5, 2010, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

This disclosure relates in general to the field of communications and,more particularly, to offloading data in a communication system.

BACKGROUND

Networking architectures have grown increasingly complex incommunications environments: particularly so in mobile wirelessenvironments. Wireless communication technologies can be used inconnection with many applications, including satellite communicationssystems, portable digital assistants (PDAs), laptop computers, mobiledevices (e.g., cellular telephones, user equipment), etc. Wirelesscommunication technologies are handling increasing amounts of datatraffic volume, and the types of data being transported through mobilewireless networks have changed dramatically. This is in part becausemobile devices have become more sophisticated and, further, such devicesare able to engage in more data-intensive activities such as streamingcontent, playing video games, videoconferencing, etc. Video,file-sharing, and other types of data-intensive traffic (moretraditionally associated with wired networks) have gradually displacedvoice as the dominant traffic in mobile wireless networks. There is asignificant challenge in coordinating which flows merit particularprocessing in order to minimize resources associated with optimallymanaging network traffic.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure andfeatures and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying figures, whereinlike reference numerals represent like parts, in which:

FIG. 1 is a simplified illustrative block diagram of a communicationsystem in accordance with one embodiment of the present disclosure;

FIG. 2A is a simplified block diagram illustrating possible exampledetails associated with the communication system in accordance with oneembodiment of the present disclosure;

FIG. 2B is a simplified flow diagram illustrating potential operationsassociated with one embodiment of the present disclosure;

FIG. 3A is a simplified block diagram illustrating possible exampledetails associated with one embodiment of the present disclosure;

FIG. 3B is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 4A is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 4B is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 5A is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 5B is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 6A is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 6B is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 7A is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 7B is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 7C-1 is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 7C-2 is a continuation of the simplified flow diagram 7C-1illustrating potential operations associated with one embodiment of thepresent disclosure;

FIG. 8A is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 8B is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 8C is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 8D is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 9A is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 9B is another simplified flow diagram illustrating potentialoperations associated with one embodiment of the present disclosure;

FIG. 9C is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 10A is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 10B is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 10C is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 10D is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 10E is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure;

FIG. 10F is another simplified block diagram illustrating one potentialoperation associated with one embodiment of the present disclosure; and

FIG. 11 is a simplified block diagram illustrating a data packetassociated with one embodiment of the present disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

Discovery

A method is provided in one example embodiment and includes receiving adata packet over a first link at a first network element; establishingan out-of-band channel over a second link between the first networkelement and a second network element; and receiving instructions at thefirst network element to offload the data packet from the first link. Inmore particular instances, the first network element can be a mobileenabled router and the second network element can be a gateway generalpacket radio service support node or a packet data network gateway.

In other examples, the method includes receiving a discovery messagefrom the second network element, the discovery message triggersestablishment of the out-of-band channel. Additionally, the data packetcan be offloaded based on the type of data in the data packet. In otherimplementations, predefined classes of traffic are provisioned such thatthe first network element is configured to map certain classes oftraffic to available backhaul links. Additionally, the method mayinclude establishing a generic routing encapsulation (GRE) tunnelbetween the first network element and the second network element usingthe out-of-band channel. In other examples, the GRE tunnel is used toloopback traffic to the first network element during handover activitiesinvolving a user equipment. Using the out-of-band channel, the firstnetwork element can be configured to identify itself, confirm receipt ofa discovery request, and obtain session control instructions.

TEID Discovery

A method is provided in one example embodiment and includescommunicating an in-band message packet from a first network element;receiving a response to the in-band message from a second networkelement, where the response may include tunnel identification bindingdata that identifies a tunnel on a backhaul link on which traffic from auser equipment can flow; and receiving instructions from the secondnetwork element to offload a received data packet from the backhaullink. In more particular instances, the in-band message can be set toloopback when the in-band message is sent from the first networkelement.

In other examples, the tunnel identification binding data is provided inthe payload of the in-band message when the in-band message is sent fromthe first network element. Additionally, the method may includereceiving an assigned IP address of the user equipment in the responseto the in-band message. In other implementations, the method may includechanging an endpoint of the in-band message at a servicing generalpacket radio service support node or serving gateway and communicatingthe in-band message to a different network element. Additionally, thesecond network element can be a gateway general packet radio servicesupport node or a packet data network gateway and the first networkelement is a mobile enabled router. In other examples, the method mayinclude receiving identification data of the gateway general packetradio service support node in the response to the in-band message.

Dormant

A method is provided in one example embodiment and includes receiving adownstream data packet transported on a backhaul link at a first networkelement, where the downstream data packet is associated with a userequipment; identifying whether a downstream tunnel used to communicatethe data packet to the user equipment has become dormant; andcommunicating an in-band message to a second network element that thedownstream tunnel is dormant. In more particular instances, the methodfurther includes dropping the data packet when a network address porttranslation binding has expired or does not exist.

In other examples, the method may include identifying the downstreamtunnel as dormant when an activity timer has expired. Additionally, themethod may include identifying the downstream tunnel as dormant based ona stale state setting. In other implementations, the method may includebuffering the data packet after identifying that the downstream tunnelused to communicate the data packet to the user equipment is dormant. Inother examples, the method may include receiving a tunnel identificationbinding that identifies a second tunnel used to communicate the datapacket to the user equipment. Additionally, the method may includeidentifying that an upstream tunnel used to communicate the data packetfrom the user equipment is dormant and communicating an in-band messageto the first network element that the upstream tunnel is dormant.

IP Routing

A method is provided in one example embodiment and includes receiving adata packet transported on a backhaul link at a first network element;de-capsulating the data packet; identifying whether the data packet isan upstream data packet; identifying whether the data packet matches aninternet protocol (IP) access control list (ACL) or a tunnel endpointidentifier; and offloading the data packet from the backhaul link. Inmore particular instances, the method includes identifying that the datapacket does not match the internet IP ACL or the tunnel endpointidentifier and communicating the data packet to a second networkelement.

In other examples, the method includes identifying that the data packetis a downstream data packet, identifying a service to be performed forthe data packet that cannot be performed at the first network element,and communicating the data packet to a second network element.Additionally, the method may include assigning an IP address to the datapacket and performing a network address translation on the data packetat a gateway general packet radio service support node. In otherimplementations, the method may include identifying that the data packetis a downstream data packet and restoring tunnel header and tunnelidentification based on the IP address of the data packet. Additionally,the method may include performing a general packet radio servicetunneling protocol sequencing. In other examples, the method may includeidentifying that the data packet is a downstream data packet, andcommunicating the data packet to a radio network controller or an eNodeB.

NAT

A method is provided in one example embodiment and includes receiving adata packet transported on a backhaul link at a first network element;identifying whether the data packet is an upstream data packet;identifying whether the data packet matches an IP ACL or a tunnelendpoint identifier; performing a network address translation on thedata packet; and offloading the data packet from the backhaul link. Inmore particular instances, the method may include identifying that thedata packet does not match the IP ACL or the tunnel endpoint identifierand communicating the data packet to a second network element.

In other examples, the method may include identifying that the datapacket is a downstream data packet and restoring a tunnel header andtunnel identification based on an IP address of the data packet.Additionally, the method may include performing a general packet radioservice tunneling protocol sequencing. In other implementations, themethod may include identifying that the data packet is a downstream datapacket, identifying that a service is to be performed for the datapacket that cannot be performed at the first network element, andperforming the network address translation on the data packet such thatthe data packet returns to a second network element. Additionally, themethod may include identifying a change to the first network element andperforming a network address translation on the data packet such thatthe data packet returns to a third network element. In other examples,the method may include identifying a carrier grade NAT to operate as ananchor point for particular user equipment traffic, and establishing atunnel associated with the first network element for the particular userequipment traffic.

Example Embodiments

Turning to FIG. 1, FIG. 1 is a simplified block diagram of an exampleembodiment of a communication system 10, which can be associated with amobile wireless network in a particular implementation. The examplearchitecture of FIG. 1 includes multiple instances of user equipment(UE) 12 a-c: each of which may connect wirelessly to a respective eNodeB (eNB) 14 a-c. Each eNB 14 a-c may be coupled to a mobility enabledrouter (MER) 50 a-c, which can be tasked with providing offloadfunctionalities for the architecture, as discussed herein. Note that thebroad term ‘offload’ as used herein in this Specification is used tocharacterize any suitable change in routing, path management, trafficmanagement, or any other adjustment that would affect packetpropagation. This can further involve any type of re-routing, directing,managing, hop designation, adjustment, modification, or changes to agiven routing path (at any appropriate time).

MERs 50 a-c can be connected to an Ethernet backhaul 18 in certainnon-limiting implementations. Communication system 10 can also includevarious network elements 22 a-f, which can be used to exchange packetsin a network environment. As illustrated in this example implementation,the architecture of communication system 10 can be logically broken intoa cell site segment, a mobile telephone switching office (MTSO) segment,a regional sites segment, and a mobile data center (DC) segment. Adefault path 60 generally indicates the default routing path for trafficpropagating in communication system 10.

A packet data network gateway/serving gateway (PGW/SGW) 20 may beconnected to Ethernet backhaul 18 (and/or a data center) through one ormore intermediate network elements. The mobile data center may include aMultimedia Messaging Service (MMS) 24 and an Internet protocol (IP)Multimedia Subsystem (IMS) 26. A Mobility Management Entity (MME) 28 isalso provided in this example for facilitating user interaction, such astracking user equipment, authenticating users, etc. Other networks,including an instantiation of an Internet 58, may be connected to themobile wireless network at various suitable locations, including atvarious network elements and Ethernet backhaul 18.

Each of the elements of FIG. 1 may couple to one another through simpleinterfaces (as illustrated), or through any other suitable connection(wired or wireless), which can provide a viable pathway for networkcommunications. Additionally, any one or more of these elements may becombined or removed from the architecture based on particularconfiguration needs. Communication system 10 may facilitate transmissioncontrol protocol/Internet protocol (TCP/IP) communications for thetransmission or reception of packets in a network, and may operate inconjunction with a user datagram protocol/IP (UDP/IP), or any othersuitable protocol where appropriate and based on particular needs.

Communication system 10 may be tied to the 3rd Generation PartnershipProject (3GPP) Evolved Packet System architecture, but alternativelythis depicted architecture may be equally applicable to otherenvironments. In general terms, 3GPP defines the Evolved Packet System(EPS) as specified in TS 23.401, TS.23.402, TS 23.203, etc. The EPSconsists of IP access networks and an Evolved Packet Core (EPC). Accessnetworks may be 3GPP access networks, such a GERAN, UTRAN, and E-UTRAN,or they may be non-3GPP IP access networks such as digital subscriberline (DSL), Cable, WiMAX, code division multiple access (CDMA) 2000,WiFi, or the Internet. Non-3GPP IP access networks can be divided intotrusted and untrusted segments. Trusted IP access networks supportmobility, policy, and AAA interfaces to the EPC, whereas untrustednetworks do not. Instead, access from untrusted networks can beperformed via the evolved PDG (ePDG), which provides for IPsec securityassociations to the user equipment over the untrusted IP access network.The ePDG (in turn) supports mobility, policy, and AAA interfaces to theEPC, similar to the trusted IP access networks.

Note that user equipment 12 a-c can be associated with clients,customers, or end users wishing to initiate a communication in system 10via some network. In one particular example, user equipment 12 a-creflects devices configured to generate wireless network traffic. Theterm ‘endpoint’ and ‘end-station’ are included within the broad termuser equipment, as used herein. User equipment 12 a-c can includedevices used to initiate a communication, such as a computer, a personaldigital assistant (PDA), a laptop or electronic notebook, a cellulartelephone, an iPhone, a Blackberry, an Android, a smartphone, a tablet,an iPad, an IP phone, or any other device, component, element,equipment, or object capable of initiating voice, audio, video, media,or data exchanges within communication system 10. User equipment 12 a-cmay also include a suitable interface to the human user, such as amicrophone, a display, or a keyboard or other terminal equipment. Userequipment 12 a-c may also be any device that seeks to initiate acommunication on behalf of another entity or element, such as a program,a database, or any other component, device, element, or object capableof initiating an exchange within communication system 10. Data, as usedherein in this document, refers to any type of numeric, voice, video,media, or script data, or any type of source or object code, or anyother suitable information in any appropriate format that may becommunicated from one point to another.

For purposes of illustrating certain example techniques of communicationsystem 10, it is important to understand the communications that may betraversing the network. The following foundational information may beviewed as a basis from which the present disclosure may be properlyexplained. IP networks may provide users with connectivity to networkedresources such as corporate servers, extranet partners, multimediacontent, the Internet, and any other application envisioned within IPnetworks. While these networks generally function to carry data plane(user-generated) packets, they may also implicate control plane andmanagement plane packets.

The term packet is used to refer to data plane packets, control planepackets, and management plane packets. In general, the data plane (alsoknown as the forwarding plane, or the user plane) provides the abilityto forward data packets; the control plane provides the ability to routedata correctly; and the management plane provides the ability to managenetwork elements. For normal IP packet processing, an IP routertypically has a data plane, a control plane, and a management plane. TheIP packets themselves support all of the planes for any IP-basedprotocol, and the IP router has no inherent knowledge about whether eachIP packet is a data, control, or management plane packet.

The vast majority of packets handled by a router travel through therouter via the data plane. Data plane packets typically consist ofend-station, user-generated packets, which are forwarded by networkdevices to other end-station devices. Data plane packets may have atransit destination IP address, and they can be handled by normal,destination IP address-based forwarding processes. Service plane packetscan be a special type of data plane packets. Service plane packets arealso user-generated packets, which may be forwarded by network elementsto other end-station devices; however, they may require high-touchhandling by a network element (above and beyond normal, destination IPaddress-based forwarding) to properly forward the packet.

Examples of high-touch handling include such functions as genericrouting encapsulation (GRE), quality of service (QoS), virtual privatenetworks (VPNs), and secure socket layer/IP security (SSL/IPsec)encryption/decryption. In a mobile network, the data plane may beresponsible for packet processing at a session/flow level, multipleflows/session per active user, access control list (ACL)/traffic flowtemplate (TFT) filters per user/flow, tunneling, rate limiting,subscriber scalability, security, and Layers 4-7 (L4-L7) inspection.These activities are typically intensive in terms of memory and packetprocessing.

Control plane packets commonly include packets that are generated by anetwork element (e.g., a router or a switch), as well as packetsreceived by the network that may be used for the creation and operationof the network itself. Control plane packets may have a receivedestination IP address. Protocols that “glue” a network together, suchas address resolution protocol (ARP), border gateway protocol (BGP), andopen shortest path first (OSPF), often use control plane packets. In amobile network, the control plane may be responsible for sessionmanagement, call setup support requirements, interfacing with externalservers (e.g., querying for per-user policy and control information),managing high availability for a gateway, and configuring and managingthe data plane. Packet overloads on an IP router's control plane caninhibit the routing processes and, as a result, degrade network servicelevels and user productivity, as well as deny specific users or groupsof users' service entirely.

Management plane packets also typically include packets that aregenerated or received by a network element. This may also includepackets generated or received by a management station that are used tomanage a network. Management plane packets may also have a receivedestination IP address. Examples of protocols that manage a deviceand/or a network, which may use management plane packets, includeTelnet, Secure Shell (SSH), Trivial File Transfer Protocol (TFTP),Simple Network Management Protocol (SNMP), file transfer protocol (FTP),and Network Time Protocol (NTP).

Typically, mobile wireless service providers have selected and deployedgateway products that combine mobile wireless specific control planefunctionality (and protocol usage) with data plane functions. The dataplane functions may be used for classification, tunneling, featureenforcement, and accounting. Such a combined functionality may be viablefor subscriber traffic models exhibiting low-data throughput and,further, having an active device population that supports data servicesin the few million range. However, as the number of subscribers and datathroughput increases, this strategy can limit the ability of serviceproviders to scale their systems accordingly.

In typical cellular networks, mobile traffic is sent over the RadioAccess Network to eNBs 14 a-c (or a Node B (UMTS)). From there, mobiletraffic is further processed by mobile packet network elements, (e.g.,RNC/SGSN/gateway GPRS support node (GGSN) (UMTS) or MME/SGW/packet datanetwork gateway (PGW) (LTE/EPC).) Throughout the cellular network, thereare many more eNBs than mobile packet elements and, hence, cellulartraffic should be backhauled from the cell site to the mobile packetcore elements. There are different backhaul network technologiesavailable; however, backhaul network technologies differ in terms ofspeeds, feeds, costs, and quality. RAN Backhaul (from the cell site) isrelatively expensive but relatively cheaper connections from the cellsite will often not come with the necessary Service Level Agreements(SLAs), etc.

Not all access technologies are available to every cell site, often morethan one is available (having different quality and cost for eachavailable backhaul network technology). In addition, synchronizationsignals for cellular network timing are often needed to cell sites.Synchronization is commonly present in legacy backhaul technologies(e.g., TDM) due to their synchronous nature. For newer non-synchronousbackhaul network technologies, synchronization can be provided viadifferent mechanisms on top of IP-based backhaul network technologies(however, some operators may not be comfortable with that situation). Abasic problem with typical cellular networks is that mobile traffic issent over “high quality” and expensive backhaul links. For example,voice traffic (high value per bit) needs a high-quality backhaul link,while best-effort Internet bound traffic (low value per bit) does notneed a high quality backhaul link.

An approach is needed that allows for different types of traffic to besent over different types of backhaul links with differentcharacteristics (and associated costs). One option would be to deploymore intelligence in the cell site (e.g., by use of deep packetinspection (DPI)), where the cell site (router) could discover the typesof traffic being sent through it, and use the corresponding appropriatebackhaul link. For example, voice traffic (high-value per bit) could besent over an expensive high quality backhaul link, while best-effortInternet bound traffic (low-value per bit) could be sent over a lessexpensive lower quality backhaul link. There are multiple problems withsuch an approach. For example, given the large number of cell sites,capex at the cell site is a significant concern, and a DPI-basedsolution is likely to increase overall cell site capex.

Similarly, opex issues argue against deploying DPI-based solutions inthe cell site. From a technical point of view, it may be difficult for aDPI-based solution to actually determine which traffic should be sent onwhich backhaul link. Encryption and encapsulation of the traffic couldcomplicate a DPI-based solution, which in turn could also increase capexand opex issues. Furthermore, a cell site router-based approach wouldaddress traffic in the upstream direction only. A solution is needed forthe downstream direction as well, especially considering that downstreamtraffic volumes generally far exceed upstream traffic volumes.

In accordance with the teachings of the present disclosure, thearchitecture discussed herein can offer a method and apparatus forrouting traffic to and from a mobile device without propagating though adefault path (e.g., SGSN/SGW, GGSN/PGW, etc.). The routers in thenetwork can be configured to perform mobile user-plane functions underthe control of one or more GGSNs/PGWs (3G/4G). To accomplish this, someGGSNs/PGWs and routers in the mobile network can include additionalfunctional enhancements. However, other deployed network nodes (RNCs,SGSNs/SGWs, Node Bs, eNode Bs, etc.) can be assumed to bestandards-based and, hence, would require no enhancements in certainimplementations of the present disclosure.

The functional enhancements added to the network elements (e.g.,routers) and GGSNs/PGWs can be referred to as MER enhancements and MERcontrol agent enhancements (MER-CA) (e.g., GGSN with 3G or theequivalent PGW control agent with 4G). MERs in the network can becontrolled by one or more MER-CAs (e.g., GGSN/PGW) to intercept andprocess mobile subscriber's traffic before such traffic reaches theGGSNs/PGWs. For instance, specific subscriber's traffic could bediverted to the Internet, transported over specific routes withdifferent QoS parameters, diverted to local content servers/caches, etc.

Consider an example in which a cell site has at least two pathsavailable to it: a low-cost low-quality path (e.g., DSL), and ahigh-cost high-quality path (e.g., TDM, ATM, or a Carrier-Ethernet).Furthermore, consider that the cell site router is enhanced/provisionedto be a MER cell site router and the pre-aggregation and/or aggregationrouters are enhanced to be MER pre-agg/agg routers, as disclosed herein.Similar, the mobile anchor gateway (e.g., GGSN/PGW), is enhanced to be aMER-CA. Based on MER-CA intelligence, the cell site router MER isinstructed which upstream traffic to backhaul over which path/link(e.g., for an extra fee, Skype/Facetime traffic can be routed on ahigh-quality path, whereas other Internet-bound traffic can be routed ona low-quality path). Similarly, the pre-aggregation or aggregation MERthat manages a particular backhaul link can be instructed whichdownstream traffic should be sent over which path/link. The level ofrouting granularity can be determined by MER-CA intelligence, forexample, session-level (e.g., looking at inner IP address or collectionof bearers/PDP contexts), bearer-level (EPS bearer, PDP context), flowor application-level, DSCP/QoS settings, etc.

Note that the flow or application-level approach may require additionalprocessing resources in the MER-CA and, hence, may not be the mostdesirable. Traffic could be routed on a certain path that is mapped to agiven bearer/PDP context, for ease of MER handling (i.e., both the MERand the MER-CA can analyze EPS bearers/PDP context). In addition,different levels of granularity are possible. The MER (whether residingin the cell site or pre-aggregation/aggregation) should be instructed onhow to handle particular traffic.

Since mobile endpoints are constantly moving, and because IP networksuse dynamic routing protocols, the cell site router and pre-agg/aggrouter serving a given flow of traffic may change. To do this, the cellsite routers and pre-aggregation/aggregation routers can be configuredas MERs in accordance with the teachings of the present disclosure. Thisallows the MERs to process MER messages, as defined in the overall MERscheme and as disclosed herein (e.g., discovery requests, which arediscussed below). Once a user session has been established, and trafficfor that session is a candidate for selective backhaul link routing, theMER-CA can identify the upstream and downstream MERs. The downstream MERdiscovery procedure can be used to accomplish this, whereby the MER-CAis configured to send an in-band “discover” message from the MER-CAtoward the user equipment (UE). This message will be forwarded insideGTP-U through the downstream MER (pre-agg/agg router), as well as theupstream MER (cell site router), provided there is one cell site routerper cell site (which is normally the case).

Both the downstream and upstream MER can identify themselves to theMER-CA, thereby establishing an out-of-band signaling association withthe MER-CA. (Out-of-band signaling can include separate signalingchannels established between MERs and associated MER-CAs.) The signalingassociation can be M:N, meaning that any MER-CA may control severalMERs, and any MER may be controlled by several MER-CAs. In-bandsignaling can include sending control information in the same GTP-Uchannels used for sending subscriber's data (e.g., default path 60).

In-band messages embedded in GTP-U channels may be used to avoid theneed for MERs to interpret existing mobile signaling protocols(RANAP/GTP-C with 3G, and GTP-C v2 with 4G). Further, in-band messagesmay enable the MER-CA to perform MER discovery such that the MER-CA candynamically discover which routers in the network are capable of being aMER or, more importantly, to dynamically discover which MER (currently)is forwarding a specific subscriber's traffic to be controlled. Inaddition, in-band messages may enable the MER-CA to discover when aspecific subscriber's traffic has moved from one MER to another MER (asin a handover scenario).

Also, in-band messages may enable MERs to perform tunnel endpointidentifier (TEID) discovery to dynamically discover upstream/downstreamTEIDs pair for a specific subscriber's traffic, and to discover themapping of two different upstream/downstream TEIDs pairs (i.e., thoseused between GGSN/SGSN, and the corresponding pair used betweenRNC/SGSN). In one particular embodiment, the TEID is a 32-bit field usedto multiplex different connections in the same GTP tunnel. In-bandmessages may enable MERs to discover new TEIDs associated with thesubscriber when existing TEIDs become dormant. In addition, in-bandmessages may allow the MER-CA to control the discovered MERs through theestablishment of direct out-of-band channels, and through sendingappropriate control messages through such out-of-band (OOB) channels(reliable/redundant and secure). In addition, in-band messages mayenable the MER-CA and MERs to exchange configuration and otherparameters without manual associations/configurations.

In-band messages are initiated/terminated on the MER-CA and MERs ((e.g.,MERs are transparent to other mobile nodes in the network). In-bandmessages can be transported by existing mobile nodes without requiringadditional enhancements (with the exception of a GGSN being enhanced toperform certain functions associated with a MER-CA). In a particularembodiment, in order to prevent in-band messages from being forwarded tounintended entities during various failure scenarios, the outer tunnel'sdifferentiated services code point (DSCP) field of in-band packets isset such that other routers at the edge of the network may be configuredto block these messages from passing to the end users; even in the caseof MER double failure (i.e., both active and redundant MER fail).

The MER to be controlled can be discovered dynamically, along with thedownstream/upstream tunnel TEID associated with a specific subscriber.This, in turn, allows the MER-CA to instruct the MER (via theout-of-band signaling channel) which downstream traffic should be sentover particular backhaul links. This can be performed in various ways,for example, the MER can inform the MER-CA about specific backhaul linksavailable, and the MER-CA can then specify the backhaul links to use forparticular types of traffic. In addition, the MER-CA can simply operatewith predefined classes of traffic, and the MER may be configured to mapthose classes of traffic to suitable backhaul links available to it(e.g., “low quality Internet”, “high quality TDM”, best effort, class ofservice (CoS) distinctions, quality of service (QoS) levels, etc.).

The cell site router MER is configured to establish backhaul linkselections for the upstream data. To do this, the cell site router MERis configured to perform upstream TEID discovery, as described below,with certain changes. Since end user traffic is not actually broken out,but rather just backhauled differently, there is no new IP address (andassociated network address translation (NAT) bindings) beingestablished. Note that this makes the overall scheme somewhat simplerthan the general MER and TEID discovery procedure discussed hereinbecause routing (backhaul) paths can be changed on the fly withoutaffecting an established session.

Similar to the downstream MER, the MER-CA can inform the upstream MERwhich traffic should be sent on which upstream links. Again, this can beaccomplished in different manners, as described above. In addition, itcan be signaled as part of the in-band discovery message, or through theout-of-band signaling channel established with the MER-CA. Once theabove signaling has been completed, downstream traffic for a particularsession can then be sent over different paths by the pre-agg/agg MERrouter, in accordance with the instructions provided by the MER-CA.Similarly, upstream traffic can be sent over different upstream paths bythe MER cell site router, in accordance with instructions from theMER-CA.

Once an endpoint becomes dormant, the GTP-U tunnel associated with theendpoint (e.g., end user 12 a) may disappear, and subsequently bereestablished with a different TEID. Similarly, TEIDs may be reusedafter some time interval. Therefore, the MERs (upstream and downstream)may maintain an inactivity timer used to detect potentially stale TEIDs.The inactivity timer may be preset based on the time it would take foran endpoint (and thus a GTP-U tunnel) to be deemed dormant. In addition,the MERs may check for TEIDs being assigned to another endpoint prior toexpiration of the inactivity timer. If the inactivity timer has expired,or if a TEID has been assigned to another endpoint, then the discoveryprocedure can be triggered again to determine the new TEID.

The upstream MER (cell site router) will often change on a handover, dueto mobility. When that happens, the downstream TEID can change as well.The downstream MER (pre-agg/agg router) may or may not change onhandover. However if it does, the new router would not know of anyspecial backhaul link selection for the downstream TEID. If the MER-CAis aware of the handover, it can simply perform the discovery proceduresas described above.

However, in many cases, the MER-CA will not know that a handover hasbeen completed (e.g., because the RNC, SGSN or SGW did not change aswell). [It should be noted that when such a case is undetected, it doesnot interfere with normal system operation; rather, there is just notany backhaul link selection in place for the traffic (e.g., defaultrouting is used instead).] The other mobile packet core elements (RNC,SGSN, SGW) may be enhanced with the MER functionality, whereby theyeither inform the MER-CA, or trigger a “stale” TEID and a “discovery”TEID procedure when handovers happen (and/or endpoints go dormant).

In addition, the MER-CA may perform periodic discovery for the targetedGTP-U tunnels. Periodic discovery may work reasonably well for usersthat experience occasional handovers during an active session. Further,the MERs may be configured with a targeted set of IP addresses, whichare candidates for selective backhaul routing. The MER can then lookinside the GTP-U tunnels, and when the MER identifies a targeted innerIP address for which the GTP-U tunnel is currently not setup forbackhaul link selection, the discovery procedure is initiated with theMER-CA to determine whether this particular GTP-U tunnel should berouted differently over the backhaul network.

Routing changes may also lead to traffic going through a differentdownstream MER router than was previously being used. To protect againstthis, the MER-CA can periodically initiate the downstream discoveryprocedure. Similarly, routing updates received by the MER may enable theMER to determine that one or more sessions no longer pass through theMER and, as a result, pass information about those sessions to theMER-CA, which can trigger a new discovery procedure.

By applying the MER principles to backhaul link selection, differenttypes of traffic can be sent on different types of backhaul linksaccording to the cost and quality tradeoffs that are appropriate forparticular types of traffic. MER-CA is enhanced to discover differentMER routers for the upstream and downstream direction, and theoptimizations performed by the MER are that of link selection, ratherthan local anchoring and breakout. This allows operators to use lowercost backhaul links for traffic that can tolerate the low quality of thebackhaul link, without degrading quality or service for traffic, whichcannot tolerate the low quality of the backhaul link, or for traffictargeted by the operator for offering the high quality backhaul link.The protocol can be deployed in a manner that does not require extensiveprovisioning or static configuration of the network infrastructure, but,rather, relies on central subscriber and traffic processing intelligencein the MER-CA (e.g., GGSN/PGW) coupled with dynamic signaling with thenetwork infrastructure. Similarly, the protocol does not require DPIprocessing capabilities in the network infrastructure, and insteaddefines mechanisms that can be implemented on router platformsthemselves.

Hence, the architecture of FIG. 1 can effectively reduce and eliminatethe constraints of previous architectures by intelligently sendingdifferent types of traffic on different types of backhaul linksaccording to cost and quality tradeoffs. Moreover, this data planegeneralization further allows more user data to be offloaded at networkelements much closer to the network edge. In one sense, the functionsdisclosed herein can be distributed across the network in order toalleviate processing that would otherwise occur at a single networkelement. This would directly reduce the downstream processingrequirements (e.g., at PGW/SGW 20).

Turning to FIG. 2A, FIG. 2A is a simplified block diagram illustratingone possible set of details associated with communication system 10.FIG. 2A includes handset 12 a and MER 50 a. FIG. 2A further includescell sites 30 a-c, a radio network controller (RNC) 32, a servinggeneral packet radio service (GPRS) support node/serving gateway(SGSN/S-GW) 34, routers 52, and GGSN/PGW 54. In a particular embodiment,GGSN/PGW 54 is a MER-CA, which includes the control agent functionsbeing discussed herein.

In general terms, cell sites 30 a-c are a site where antennas andelectronic communications equipment are used (e.g., provisioned on aradio mast or tower) to create a cell in communication system 10.Routers 52 may be enhanced and converted to MERs. (MER 50 a and MER 50 bare an enhanced version of a router 52 deployed in communication system10.) The elements shown in FIG. 2A may couple to one another throughsimple interfaces (as illustrated) or through any other suitableconnection (wired or wireless), which provides a viable pathway fornetwork communications. Additionally, any one or more of these elementsmay be combined or removed from the architecture based on particularconfiguration needs.

In a particular embodiment, handset 12 a communicates data to one ormore cell sites 30 a-c. From cell sites 30 a-c, the data propagates toeither RNC 32, which communicates the data to MER 50 a, or directly toMER 50 a. The data is communicated from MER 50 a to a core network 56(e.g., an IP or a multiprotocol label switching (MPLS) network) throughSGSN/SGW 34, routers 52 and 52 b, and GGSN/PGW 54 on default path 60.Operationally, MER 50 a may be configured to breakout the data (or apacket of data) and communicate the data to a destination that is not ondefault path 60. For example, MER 50 a may communicate the data toInternet 58 using a breakout path 106.

Note that data may travel on default path 60 in various manners. Forexample, in a particular embodiment, communication system 10 may includea GPRS core network. The GPRS core network transmits IP packets toexternal networks such as core network 56 and, further, providesmobility management, session management, and transport for InternetProtocol packet services in GSM and WCDMA networks. The GPRS corenetwork may also provide support for other additional functions such asbilling and lawful interception. The GPRS core network may use tunnelingto allow UE 12 a to be moved from place to place, while continuing to beconnected to communication system 10. In a particular embodiment, thetunneling is created using a GPRS tunneling protocol. The protocolallows end users (or users of UE 12 a) to move, while continuing toconnect as if from one location (e.g., at GGSN/PGW 54) by carrying theend user's data from the SGSN to the GGSN/PGW tasked with handling thesubscriber's session.

Typically, when data from UE 12 a is initially communicated tocommunication system 10, a first upstream tunnel and second downstreamtunnel are created from RNC 32, through MER 50 a, to SGSN 34. Inaddition, a second upstream tunnel and a first downstream tunnel arecreated from SGSN 34 to GGSN 54. Each tunnel can have a uniqueTEID/source IP address.

RNC 32 may be configured as a governing element in a universal mobiletelecommunications system (UMTS) (one of the third-generation (3G)mobile telecommunications technologies, also being developed into a 4Gtechnology) or in a radio access network universal terrestrial radioaccess network (UTRAN), and can be responsible for controlling any nodeB (e.g., eNBs 14 a-c that are connected to RNC 32). [Note that node B(eNB 14 a-c) is a term used in UMTS, and is generally equivalent to thebase transceiver station (BTS) description used in GSM, and, further,reflects the hardware that is connected to the mobile phone network thatcommunicates directly with mobile handsets.]

RNC 32 can carry out radio resource management, mobility managementfunctions, and may be the point where encryption (if any) is performedbefore data is sent to (and from) UE 12 a. RNC 32 communicates the datato MER 50 a. MER 50 a may route some or all of the data to SGSN/SGW 34along default path 60 and, further, may route some or all of the data toa destination other than SGSN/SGW 34 on breakout path 106. [Note thatthis includes using breakout path 106 to allow MER 50 a to directlycommunicate with GGSN/PGW (e.g., using a GRE tunnel) as is describedbelow.] In a particular embodiment, there is more than one breakout path106 and the number of breakout paths 106 may depend on the networks orelements in communication with MER 50 a.

SGSN/SGW 34 is configured for the delivery of data to (and from) mobilestations within its geographical service area. SGSN/SGW 34 tasks mayinclude packet routing and transfer, logical link management, andauthentication and charging functions. In a particular embodiment,SGSN/SGW 34 stores location information (e.g., current cell, currentVLR) and user profiles (e.g., international mobile subscriber identity(IMSI), address(es) used in the packet data network) of GPRS users thatare registered with the SGSN/SGW 34. SGSN/SGW 34 may also be configuredto de-tunnel GTP packets from GGSN/PGW 54 for downstream traffic, tunnelIP packets toward GGSN/PGW 54 for upstream traffic, and perform mobilitymanagement (e.g., in standby mode) as a mobile moves from one routingarea to another routing area.

GGSN/PGW 54 may be a component of a GPRS network and reflects the anchorpoint, which affords mobility to UE 12 a in communication system 10(e.g., the GPRS/UMTS networks.) GGSN/PGW 54 maintains the routing usedto tunnel protocol data units (PDUs) to the SGSN/PGW (e.g., SGSN/SGW34), which services UE 12 a. GGSN/PGW 54 is the tunnel endpoint for aGGSN/PGW specific GTP-tunnel. GGSN/PGW 54 can be (indirectly) selectedby the end user at setup of a packet data protocol (PDP) context. Froman addressing perspective, GGSN/PGW 54 represents the point of presencefor ‘logged on’ end users (i.e., end users with an establishedPDP-context). Addresses can be dynamically assigned (fetched from anexternal server or a pool of owned addresses) or statically assigned.GGSN/PGW 54 may be configured to perform functions such as tunnelmanagement, IP address management, charging data collection/output,security management, packet filtering, packet routing/tunneling, QoSmanagement, and element management (particularly MER 50 a management).

GGSN/PGW 54 may be configured for the interworking between elements ofcommunication system 10 and external packet switched networks (e.g.,like core network 56). From a network external to communication system10, GGSN/PGW 54 can appear as a router to a sub-network, becauseGGSN/PGW 54 may “hide” the infrastructure of communication system 10from the external network. In a particular embodiment, GGSN/PGW 54 candetermine if a specific user (UE 12 a) is active when GGSN/PGW 54receives data addressed to the specific user. If the specific user isactive, GGSN/PGW 54 can forward the received data to SGSN/SGW 34 servingthe specific user. However, if the specific user is inactive, then thedata may be discarded. In a particular embodiment, mobile-originatedpackets are routed to the correct network by GGSN/PGW 54.

GGSN/PGW 54 can convert the GPRS packets (propagating from SGSN/SGW 34)into the appropriate packet data protocol (PDP) format (e.g., IP orX.25), and then communicate the packets on a corresponding packet datanetwork. In the other direction, PDP addresses of incoming data packetscan be mapped to a particular GTP tunnel and then sent on that GTPtunnel (towards SGSN/SGW 34, or, if a direct tunnel is used in 3G, thedata packets may be sent to RNC 32. The readdressed packets are sent tothe responsible SGSN/SGW 34. For this purpose, GGSN/PGW 54 may store thecurrent SGSN/SGW 34 address and profile of the user in a locationregister. GGSN/PGW 54 can be responsible for IP address assignment andmay be the default router for the connected specific user (UE 12 a).GGSN/PGW 54 may also perform authentication and billing/chargingfunctions. Other functions include subscriber screening, IP Poolmanagement and address mapping, QoS, and PDP context enforcement.

An out-of-band channel 73 can be used by GGSN/PGW 54 and MER 50 a tocommunicate data without having to send the data on default path 60. Bynot using default path 60, the data may be on a path with differentattributes (e.g., a more reliable and redundant path or a lessexpensive, lower quality path, etc.) than default path 60. In addition,the data being communicated between GGSN/PGW 54 and MER 50 a does notadd to the traffic already on default path 60. Using out-of-band channel73, GGSN/PGW 54 can control MER 50 a and can communicate offloadinstructions and other information (such as configuration parameters) toMER 50 a.

Turning to FIG. 2B, FIG. 2B is a simplified flowchart 200 illustratingone potential operation associated with the present disclosure. In 202,a data packet is communicated to a MER from a UE. For example, UE 12 amay communicate a data packet to MER 50 a. In 204, based on instructionsfrom a GGSN/PGW, the MER determines if the data packet should beoffloaded from a default path. If the MER determines that the datapacket should not be offloaded, then the data packet can continue alonga default path, as illustrated in 206. For example, the data packet maycontinue along default path 60. If the MER determines that the datapacket should be offloaded, then the data packet can be offloaded fromthe default path, as illustrated in 208. For example, MER 50 may offloadthe data packet from default path 60 using breakout path 106 and,subsequently, communicate the data packet to Internet 58.

Turning to FIG. 3A, FIG. 3A is a simplified block diagram illustratingone possible set of details associated with communication system 10.FIG. 3A includes handset 12 a, (e)NB 14 a, RNC 32, MER 50 a, SGSN/SGW34, and GGSN/PGW 54. MER 50 a includes a respective processor 64 a, atraffic offload module 66, and a respective memory element 68 a.GGSN/PGW 54 includes a respective processor 64 b, a MER control module74, and a respective memory element 68 b. A first upstream tunnel 76connects RNC 32 to SGSN/SGW 34 through MER 50. A second upstream tunnel78 connects SGSN/SGW 34 to GGSN/PGW 54. Second upstream tunnel 78 maypropagate through a router (e.g., router 52 shown in FIG. 2A) or a MERsimilar to MER 50 a but located further upstream (for example, if router52 was configured to be MER 50 b).

In a particular embodiment, MER 50 a is located at the borders betweennetworks/network segments. While MER 50 a may be almost any enhancednetwork element in communication system 10, the closer that MER 50 a isto UE 12 a, the earlier MER 50 a can offload traffic from default path60. A first downstream tunnel 80 can connect GGSN/PGW 54 to SGSN/SGW 34.A second downstream tunnel 82 can connect SGSN/SGW 34 to RNC 32 throughMER 50 a. Second upstream tunnel 78 and first downstream tunnel 80 maycouple through a router (e.g., router 52 shown in FIG. 2A) or a MERsimilar to MER 50 b shown in FIG. 2A.

GGSN/PGW 54 can use MER control module 74 to control MER 50 a and enableMER 50 a to perform user-plane functions for both packet and circuitmode communication, particularly offloading traffic from the corenetwork (e.g., default path 60). MER 50 a uses traffic offload module toperform the user-plane functions and, further, offload traffic asinstructed by GGSN/PGW 54. MER 50 a may also be configured to handlemedia processing (e.g., speech coding. conference call bridging etc),media generation of tones etc., setup and release of user data bearers,provision of traffic/charging info for packet mode communication,security management, routing and switching QoS management, and elementmanagement.

Out-of-band channel 73 is a separate signaling channel establishedbetween MER 50 a and GGSN/PGW 54. Out-of-band signaling 72 referencescommunication between MER 50 a and GGSN/PGW 54 that does not occur overdefault path 60. In-band signaling 70 references communication betweenMER 50 a and GGSN/PGW 54 (and other elements) using default path 60. Ina particular embodiment, the out-of-band signaling 72 association is M:Nmeaning that any GGSN/PGW 54 may control several MERs, and any MER maybe controlled by several GGSNs/PGWs 54. Out-of-band channel 73 is usedto establish a GRE tunnel 84 between MER 50 a and GGSN/PGW 54. GREtunnel 84 is used to loopback traffic to MER 50 a during handovers anddiscovery procedures and, further, may be used to communicate data toGGSN/PGW 54 that cannot be processed or serviced by MER 50 a. Bufferingof user traffic during these procedures can be performed on eitherGGSN/PGW 54 or MER 50 a or both (implementation dependent).

First upstream tunnel 76, second upstream tunnel 78, first downstreamtunnel 80, and second downstream tunnel 82 can be part of default path60. In addition first upstream tunnel 76, second upstream tunnel 78,first downstream tunnel 80, and second downstream tunnel 82 may be GTP-Utunnels and each may have a unique TEID/source IP address. Initially,MER 50 a does not know the TEID for first upstream tunnel 76, secondupstream tunnel 78, first downstream tunnel 80, and second downstreamtunnel 82 and, therefore, cannot control UE 12 a's traffic withoutknowing the TEIDs for first upstream tunnel 76 and second downstreamtunnel 82. Using out-of-band channel 73 and TEID discovery procedure,GGSN/PGW 54 communicates the TEID for first upstream tunnel 76 andsecond downstream tunnel 82 such that MER 50 a knows which UE's trafficis to be controlled and how the UE's traffic should be controlled (e.g.,if any traffic from UE 12 a should be offloaded).

GGSN/PGW 54 does not actually know the TEIDs (unless a direct tunnel hasbeen created). Hence, GGSN/PGW 54 relies on MER 50 a to perform TEIDdiscovery and communicate the TEIDs to GGSN/PGW 54 (this may beindirectly through a GTP-U tunneled path). GGSN/PGW 54 in turn, sends apacket back towards MER 50 a thereby enabling download TEID discovery,as well as determining if the upstream TEID (GTP-U tunnel) really was tobe off-loaded in the first place (e.g. overlapping IP-addresses couldcause a false trigger in the MER). Once TEID discovery is done, GGSN/PGW54 and MER 50 a can communicate directly (e.g. through GRE tunnel 84)and exchange information about what traffic needs to be off-loaded basedon the TEID information exchanged.

Once MER 50 a knows the TEID of first upstream tunnel 76 and seconddownstream tunnel 82, traffic can be offloaded from default path 60, andwhen the traffic for UE 12 a is returned, MER 50 a can communicate thedata in the returned traffic to UE 12 a. In a particular embodiment, ifdata is returned to MER 50 a and the returned data needs to propagatethrough GGSN/PGW 54, then MER 50 a can communicate that data to GGSN/PGW54 using GRE tunnel 84. GGSN/PGW 54 may similarly return the data to MER50 a using GRE tunnel 84 or using first downstream tunnel 80.

Turning to FIG. 3B, FIG. 3B is a simplified flowchart 300 illustratingone potential operation associated with the present disclosure. In 302,a data packet can be sent from user equipment requesting a connection tothe mobile network. For example, a data packet may be sent from UE 12 ato RNC 32. In 304, GTP-U tunnels are established. For example, firstupstream tunnel 76, second upstream tunnel 78, first downstream tunnel80, and second downstream tunnel 82 may be established. In 306, anout-of-band channel is established between a MER and a GGSN. Forexample, out-of-band channel 73 may be established between MER 50 a andGGSN/PGW 54. In 308, using the out-of-band channel, the MER can receivedata packet offload information from the GGSN. For example, GGSN/PGW 54may communicate data packet offload information (including TEIDs) to MER50 a using out of channel band 73.

MER Discovery and Path Selection

Turning to FIG. 4A, FIG. 4A is a simplified block diagram ofcommunication system 10, which (in this particular implementation) mayinclude UE 12 a, cell site 30 a-d, RNCs 32 a-g, MER 50 a-c, SGSN/SGW 34a-c, and GGSN/PGW 54 a-c. When UE 12 a attaches to the mobile networkand requests connection through control plane messages, several GTP-U(user plane) tunnels may be established, (for example, first upstreamtunnel 76, second upstream tunnel 78, first downstream tunnel 80, andsecond downstream tunnel 82 may be established on default path 60). Theuser plane data packet may propagate through one of cell sites 30 a-d(e.g., cell site 30 d) and through one of RNC 32 a-g (e.g., RNC 32 e).The data packet can travel through first upstream tunnel 76 to MER 50 b.In a particular embodiment, at MER 50 b, a MER identifier is added to anew data packet (in-band message) using the same tunnel identifier asthe received user data and the new data packet is communicated toSGSN/SGW 34 b and on to GGSN/PGW 54 a via second upstream tunnel 78. TheMER identifier may be an identifier that identifies MER 50 b and informsGGSN/PGW 54 a that MER 50 b is not just a router, but has been enhancedand configured to behave as a MER.

GGSN/PGW 54 a sends a MER discovery message (which can be triggered bythe first upstream packet arriving at GGSN/PGW 54 a or immediately afterfirst upstream tunnel 76, second upstream tunnel 78, first downstreamtunnel 80, and second downstream tunnel 82 are established) to SGSN/SGW34 b via first downstream tunnel 80. The MER discovery message travelsfrom SGSN/SGW 34 b to MER 50 b via second downstream tunnel 82.Typically, the message would pass through MER 50 b and onto RNC 32 e;however, MER 50 b intercepts the MER discovery message and establishesout-of-band channel 73 with GGSN/PGW 54 a. By establishing out-of-bandchannel 73 between MER 50 b and GGSN/PGW 54 a, GGSN/PGW 54 a can controlMER 50 b and, further, can communicate offload instructions and otherinformation (such as configuration parameters) for MER 50 b.

While it is possible to manually configure static associations of eachMER with RNCs/SGSNs, such a paradigm can be error-prone, lackflexibility, present management issues, and failed to work in manydeployment scenarios. In a particular embodiment, each GGSN/PGW 54 a incommunication system 10 may be configured to discover which MER in thenetwork is currently forwarding the traffic from/to a specific UE (e.g.,UE 12 a), send session control instructions to the discovered MERrelated to the required treatment of the specific UE's traffic, discoverwhen the specific UE moves from one MER to another (e.g., in a handoverscenario), and send control information to the new MER.

In one particular embodiment, a MER identifier is not added to the datapacket by MER 50 b. Usage of in-band signaling (not shown) can allowGGSN/PGW 54 a to embed discovery messages in the GTP-U tunnels that werealready established for a specific UE. For example, after GGSN/PGW 54 afirst receives the data from UE 12 a, GGSN/PGW 54 a can send thediscovery message to MER 50 b using first downstream tunnel 80 andsecond downstream tunnel 82.

Because the discovery message can follow the same path as UE's 12 atraffic, if a MER is present in the path, the MER can always bediscovered without prior configurations. No special procedures would berequired on other network nodes to pass through such traffic.Interception and interpretation of the embedded messages within thesediscovery messages can be performed at the MER. Note that such messagesare not forwarded to end users (end points) in particularimplementations of the present disclosure. Because of the establishmentof direct/secure signaling channels between MERs and because control ofGGSN/PGWs occurs without prior configurations, the MER discoveryprocedure is dynamic in nature, does not require manual associations,and operates in a multitude of deployment scenarios.

Dynamic discovery of MER 50 b is enabled by passing IP addresses/portsand protocols, supported by GGSN/PGW 54 a within the in-band discoverymessage. Further, when UE's 12 a traffic moves from one MER to anotherMER (e.g., traffic is moved from MER 50 b to MER 50 a), the new MER (MER50 a) initially forwards such traffic to GGSN/PGW 54 a since it does notyet have instructions from GGSN/PGW 54 a regarding UE's 12 a traffic.Upon receiving the traffic from the new MER (MER 50 a), the GGSN/PGW 54a is triggered to initiate another MER discovery procedure in whichGGSN/PGW 54 a discovers the new MER (MER 50 a) and instructs the new MERto perform the appropriate handling. During the MER discovery procedure,UE's 12 a traffic in the upstream direction, if any, can be buffered ateither the new MER or GGSN/PGW 54 a or both (i.e., it can beimplementation dependent). The MER discovery procedure can be used inboth direct tunnel (DT) and non-DT cases.

Turning to FIG. 4B, FIG. 4B is a simplified flowchart 400 illustratingone potential operation associated with the present disclosure. In 402,a subscriber attaches to a network and requests a connection. Forexample, a subscriber may use UE 12 a to attach to communication system10 and request a connection with cell site 30 d. In 404, GPRS-U tunnelsare established for the subscriber's traffic. For example, firstupstream tunnel 76, second upstream tunnel 78, first downstream tunnel80, and second downstream tunnel 82 may be established on default path60 for UE's 12 a traffic. In 406, GGSN sends (to a MER) a discoverymessage via the GPRS tunnels. For example, GGSN/PGW 54 a may send MER 50b a discovery message using first downstream tunnel 80, and seconddownstream tunnel 82.

In 408, the mobile enabled router intercepts the discovery message. Forexample, MER 50 b may intercept the MER discovery message sent fromGGSN/PGW 54 a. In 410, the MER can establish a direct communicationchannel (out-of-band channel) with the GGSN. For example, MER 50 b mayestablish out-of-band channel 73 with GGSN/PGW 54 a. In 412, the MERidentifies itself to the GGSN, confirms receipt of the discoveryrequest, and obtains session control instructions and otherconfiguration parameters. For example, using out-of-band channel 73, MER50 b may be configured to identify itself to GGSN/PGW 54 a, confirmreceipt of the discovery request, and obtain session controlinstructions and other configuration parameters from GGSN/PGW 54 a.

TEID Discovery

Turning to FIG. 5A, FIG. 5A is a simplified block diagram ofcommunication system 10, which (in this particular implementation) mayinclude UE 12 a, cell sites 30 a-d, RNCs 32 a-g, MER 50 a-c, SGSN/SGW 34a-c, and GGSN/PGW 54 a-c. In most deployment scenarios, multiple GTP-Utunnels can be established for the same subscriber's traffic. Forexample, first upstream tunnel 76 (UL-TEID-1) and second downstreamtunnel 82 (DL-TEID-2) can be established between SGSN/SGW 34 b and RNC32 e, and second upstream tunnel 78 (UL-TEID-3) and first downstreamtunnel 80 (DL-TEID-4) can be established between SGSN/SGW 34 b andGGSN/PGW 54 a.

GGSN/PGW 54 a can identify the TEID for second upstream tunnel 78(UL-TEID-3) and first downstream tunnel 80 (DL-TEID-4). Depending on thescenario, MER 50 b may know only the TEID for first upstream tunnel 76(UL-TEID-1) and second downstream tunnel 82 (DL-TEID-2), or MER 50 b maynot know any TEIDs. Thus, if GGSN/PGW 54 a attempts to instruct MER 50 babout the treatment of UE's 12 a traffic, there is no simple commonreference. Furthermore, the inner IP address assigned to UE 12 a is notunique either (i.e., it cannot be used as a common reference), becauseoverlapping IP address support is commonly required. Hence, a TEIDdiscovery procedure needs to be employed to discover the TEID of firstupstream tunnel 76 (UL-TEID-1), second downstream tunnel 82 (DL-TEID-2),second upstream tunnel 78 (UL-TEID-3), and first downstream tunnel 80(DL-TEID-4) and the bindings of these tunnels to UE 12 a.

In a particular embodiment, when a data packet is first sent from UE 12a through communication system 10, first upstream tunnel 76, secondupstream tunnel 78, first downstream tunnel 80, and second downstreamtunnel 82 may be established (e.g., on default path 60). The data packetcan be communicated to cell site 30 d and to RNC 32 e. Using firstupstream tunnel 76, from RNC 32 e, the packet can be communicated toSGSN/SGW 34 b, through MER 50 b. Using second upstream tunnel 78, fromSGSN/SGW 34 b, the data packet can also be communicated to GGSN/PGW 54a.

GGSN/PGW 54 a can receive the data packet and, in response, communicatea MER discovery message to SGSN/SGW 34 b using first downstream tunnel80. Using the second download link tunnel 82, SGSN/SGW 34 b communicatesthe MER discovery message to MER 50 b. Typically, the message would passthrough MER 50 b and onto RNC 32 e; however, MER 50 b can intercept theMER discovery message and establish out-of-band channel 73 with GGSN/PGW54 a, if one does not yet exist. By establishing out-of-band channel 73between MER 50 b and GGSN/PGW 54 a, GGSN/PGW 54 a can control MER 50 band, further, communicate offload instructions and other information(such as configuration parameters) to MER 50 b.

In order to be able to control the traffic of a specific UE (e.g., UE 12a), each GGSN/PGW 54 a in communication system 10 can be configured todiscover which MER in the network is currently forwarding the trafficfrom/to that UE (e.g., because GGSN/PGW 54 a received traffic from UE 12a, and GGSN/PGW 54 a has the intelligence to discover the particular MERthat is handling the traffic for UE 12 a). In addition, each GGSN/PGW 54a in communication system 10 can be configured to send session controlinstructions to the discovered MER related to the required treatment ofthe UE's traffic and, further, discover when the UE moves from one MERto another (as in a handover scenario) and subsequently send controlinformation to the new MER.

In a particular embodiment, MER 50 b sends an in-band message (GTP-Upacket) in first upstream tunnel 76 in an attempt to discover theassociated TEIDs of first upstream tunnel 76 (TEIDs-1-4 bindings in thisexample). Within the in-band message, UL-TEID-1 is embedded in thepayload and the type of message is set to loopback. When the in-bandmessage arrives at SGSN/SGW 34 b, SGSN/SGW 34 b can treat the packet asany other user packet and change the TEID to match the TEID of thesecond upstream tunnel 78 (TEID-3, in this example), and pass the packetto the appropriate GGSN/PGW 54 a. (Note that the contents of theembedded payload are not necessarily modified by SGSN/SGW 34 b, just theouter tunnel could be modified.)

When the in-band message arrives at GGSN/PGW 54 a, GGSN/PGW 54 a canintercept (i.e., receive) the in-band message and form the requestedloopback function based on the embedded message type. If the MER did notinclude such information in the message, as is applicable to certaindeployment cases, GGSN/PGW 54 a may add TEID-3/4 mapping to the payloadof an in-band loopback packet (the loopback response to the in-bandmessage) before performing the loopback. GGSN/PGW 54 a can communicatethe in-band loopback packet to SGSN/SGW 34 b on first downstream tunnel80. Using second downstream tunnel 82, SGSN/SGW 34 b can communicate thein-band loopback packet to RNC 32 e.

When the in-band loopback packet arrives at MER 50 b, on the way to RNC32 e, MER 50 b intercepts and interprets the embedded message, which mayinclude the TEIDs bindings (as well as other parameters, such as theassigned IP address to UE 12 a and GGSN/PGW 54 a). At this juncture, MER50 b understands which UE's 12 a traffic is to be controlled and isready to implement whatever policies the GGSN/PGW 54 a may dictaterelated to traffic from UE 12 a. In one particular embodiment, MER 50 bmay also establish out-of-band channel 73 with GGSN/PGW 54 a.

Turning to FIG. 5B, FIG. 5B is a simplified flowchart 500 illustratingone potential operation associated with the present disclosure. In 502,a MER sends an in-band message packet in a tunnel that the MER isattempting to discover. In a particular embodiment, a TEID can beembedded in the payload of the packet, where the message is set toloopback. For example, MER 50 b may send an in-band message packet onfirst upstream tunnel 76, and the TEID (UL-TEID-1) can be embedded inthe payload of the packet. (The message can be embedded in the payloadsuch that a GGSN/PGW would be able to determine the TEID of firstupstream tunnel 76.)

In 504, when the packet arrives at an SGSN, the SGSN treats the packetas any other UE packet by changing the TEID and communicating the packetto an appropriate GGSN. (Note that the contents of the embedded payloadare not modified by the SGSN, simply the outer tunnel is modified.) Forexample, SGSN/SGW 34 b may change the outer tunnel TEID from UL-TEID-1to UL-TEID-3 and communicate the packet to GGSN/PGW 54 a. In 506, whenthe packet arrives at the GGSN, the GGSN intercepts and interprets thein-band message packet. For example, when the packet arrives at GGSN/PGW54 a, GGSN/PGW 54 a intercepts and interprets the in-band messagepacket.

In 508, the GGSN can add TEID bindings (as well as other parameters suchas the assigned IP address of the UE) and perform the requested loopbackfunction. In a particular embodiment, the GGSN may add TEID-3/4 mappingto the payload of the message (if the MER did not include suchinformation in the message) before performing the loopback. In 510, theGGSN can communicate the loopback packet to the appropriate SGSN, whichforwards it to an appropriate RNC. For example, using first downstreamtunnel 80, GGSN/PGW 54 a may communicate the in-band loopback packet toSGSN/SGW 34 b and SGSN/SGW 34 b may communicate the in-band loopbackpacket to RNC 32 e. In 512, when the loopback packet arrives at the MER(in route to the RNC), the MER intercepts and interprets the embeddedmessage, which may include the TEIDs bindings (as well as otherparameters, such as the assigned IP address to the subscriber). At thispoint, MER 50 b understands which UE's 12 a traffic is to be controlled,and is ready to enforce policies being dictated (e.g., by GGSN/PGW 54 a)for UE's 12 a traffic.

In a particular embodiment, the TEID discovery procedure described abovemay be repeated when the TEIDs at MER 50 b become stale due toinactivity/timeout, or when TEID conflicts are detected (such as thesame TEID is reused by another subscriber after UE 12 a has becomedormant). The TEID discovery procedure may not be needed in the case ofDT deployments in which just one pair of TEIDs can be used, where boththe GGSN/PGW 54 a and MER 50 b identify the same pair. The TEIDdiscovery procedure can be used with non-DT deployments.

Turning to FIG. 6A, FIG. 6A is a simplified block diagram ofcommunication system 10, which (in this particular implementation)includes UE 12 a, cell site 30 a, MER 50 a, MER 50 b, RNC 32, SGSN/SGW34 a, GGSN/PGW 54 a, and a data transmission network 62. MER 50 a can bein communication with GGSN/PGW 54 a through out-of-band signalingchannel 73 a. MER 50 b can be in communication with GGSN/PGW 54 athrough out-of-band signaling channel 73 b. In one particularembodiment, data transmission network 62 may include service providerdigital subscriber line (DSL) network 114, fiber to the x (FTTx) network116 (which is a generic term for any broadband network architecture thatuses optical fiber in last-mile), Ethernet network 118, and asynchronous optical networking/synchronous digital hierarchy (SONET/SDM)network 120. Each network in data transmission network 62 may have acost-to-quality ratio, where the cost of using the network is related tothe quality of the network.

Data transmission network 62 represents a series of points or nodes ofinterconnected communication paths for receiving and transmittingpackets of information that propagate through communication system 10.Data transmission network 62 offers a communicative interface betweensources and/or hosts, and may be any local area network (LAN), wirelesslocal area network (WLAN), metropolitan area network (MAN), Intranet,Extranet, WAN, virtual LAN (VLAN), virtual private network (VPN), or anyother appropriate architecture or system that facilitates communicationsin a network environment. Data transmission network 62 may implement aUDP/IP connection and use a TCP/IP communication language protocol inparticular embodiments of the present disclosure. A network can compriseany number of hardware or software elements coupled to (and incommunication with) each other through a suitable communications medium.Data transmission network 62 may include the network elements tofacilitate data transmission on communication system 10.

Note that DSL network 114, FTTx network 116, Ethernet network 118, andSONET/SDM network 120 may each contain network elements in a particularembodiment of the present disclosure. Each network element may includeany suitable hardware, software, components, modules, interfaces, orobjects operable to exchange information in a network environment.

In a particular embodiment, certain classes of traffic are defined suchthat low quality traffic propagates over one network (for example, datamay be sent over a low quality network such as DSL network 114) whilehigh quality traffic propagates over another network (for example, avoice call may be sent over a high quality network such as SONET/SDMnetwork 120). Traffic may be sent over a path based on a variety offactors such as a type or level of service purchased by a user, the typeof data, the current amount of traffic on a specific network, etc.Because both MER 50 a and MER 50 b should know which type of data shouldbe sent on a network, GGSN/PGW 54 a should send a discovery message toMER 50 a and MER 50 b in order to establish communications with MER 50 aand MER 50 b. The discovery process is similar to the discovery processdescribed above except, both MER 50 a and 50 b should be discovered.When the discovery message reaches MER 50 b, MER 50 b communicates thediscovery message to MER 50 a. After receiving the discovery message MER50 a establishes out-of-band channel 73 a with GGSN/PGW 54 a and MER 50b establishes out-of-band channel 73 b with GGSN/PGW 54 a and eachidentifies themselves to GGSN/PGW 54 a.

For example, once a user session has been established using UE 12 a, andtraffic for that session is a candidate for selective backhaul linkrouting, GGSN/PGW 54 a can identify the upstream MER (MER 50 a) and thedownstream MER (MER 50 b). To identify MER 50 a and MER 50 b, GGSN/PGW54 a can use a downstream MER discovery procedure, whereby GGSN/PGW 54 asends an in-band discovery message towards UE 12 a. The in-band discovermessage is communicated along default path 60 to MER 50 b (pre-agg/aggrouter), as well as to MER 50 a (cell site router, provided there is onecell site router per cell site (which is normally the case)).

Both MER 50 a and MER 50 b can identify themselves to GGSN/PGW 54 a andestablish out-of-band channels 73 a and 73 b respectively. Out-of-bandchannel 73 a can be used by GGSN/PGW 54 a to instruct MER 50 a aboutwhich upstream traffic should be sent over which link. Out-of-bandchannel 73 b can be used by GGSN/PGW 54 a to instruct MER 50 b aboutwhich downstream traffic should be sent over which link. In addition, ina particular embodiment, MER 50 b is identified, and a GRE tunnel (e.g.,GRE tunnel 84 (not shown)) is created between MER 50 b and GGSN/PGW 54a.

In a particular embodiment, MER 50 a and/or MER 50 b may communicate toGGSN/PGW 54 a about specific links available. GGSN/PGW 54 a can thenspecify which links to use for particular types of traffic. In anotherparticular embodiment, GGSN/PGW 54 a can simply communicate predefinedclasses of traffic to MER 50 a and MER 50 b. MER 50 a and/or MER 50 bcan then map those classes of traffic to suitable backhaul linksavailable (e.g., “low quality Internet,” “high quality TDM,” etc.).

In one particular embodiment, MER 50 a can establish a backhaul linkselection for the upstream traffic. To achieve the backhaul linkselection, MER 50 a can perform upstream TEID discovery as describedabove (except, because end user traffic is not necessarily broken out,but rather just backhauled differently, there is no new IP address andassociated NAT bindings being established). [Note that this makes theoverall scheme somewhat simpler than a general MER and TEID discoveryprocedure (including handover), since routing (backhaul) paths can bechanged on the fly without affecting an established session (in contrastto the anchor breakout described in the general MER solution).]

Once the signaling described above has been completed, downstreamtraffic for a particular session may be communicated over differentpaths by the pre-agg/agg MER (MER 50 b), in accordance with theinstructions provided by GGSN/PGW 54 a. Similarly, upstream traffic maybe communicated over different upstream paths by the cell site MER (MER50 a), in accordance with instructions provided by GGSN/PGW 54 a. Byrouting traffic across an appropriate network, an acceptablecost-to-quality ratio may be achieved for the architecture.

Turning to FIG. 6B, FIG. 6B is a simplified flowchart 600 illustratingone potential operation associated with the present disclosure. In 602,a MER receives network traffic. For example, MER 50 a may receivetraffic from cell site 30 a. In 604, the MER can determine which type oftraffic was received. In 606, the MER determines which type of networkmay be used to communicate the traffic and, subsequently, communicatesthe traffic using the determined network. For example, MER 50 a maydetermine that the traffic is data traffic and that DSL network 114 canbe used to communicate the traffic. MER 50 a may then communicate thetraffic over DSL network 114.

Dormant Mode

Turning to FIG. 7A, FIG. 7A is a simplified block diagram ofcommunication system 10, which (in this particular implementation)includes UE 12 a, cell sites 30 a-d, RNCs 32 a-g, MERs 50 a-c, SGSN/SGWs34 a-c, and GGSN/PGWs 54 a-c. First, upstream tunnel 76 and firstdownstream tunnel 82 connects RNC 32 e with SGSN/SGW 34 b. Second,upstream tunnel 78 and second downstream tunnel 80 connects SGSN/SGW 34b with GGSN/PGW 54 a.

Mobile terminals often shift to dormant mode to save power. Note thatthe term ‘dormant’ as used herein in this Specification encompasses anytype of staleness characteristic, timeout, timing parameter expiration,or any other suitable characteristic that would be indicative of sometype of dormancy. During dormancy events, the assigned first upstreamtunnel 76 and first downstream tunnel 82 between RNC 32 e and SGSN/SGW34 b can be released. The first upstream tunnel 76 and first downstreamtunnel 82 may be reassigned to other subscribers. In certain deploymentscenarios, specifically when direct tunneling is employed, GGSN/PGW 54 acan become aware of such events and instruct MER 50 b accordingly.However, in a general deployment case, it is possible that neitherGGSN/PGW 54 a nor MER 50 b know that the first upstream tunnel 76 andfirst downstream tunnel 82 have been released (and possibly reassigned).[Note that second upstream tunnel 78 and second downstream tunnel 80 maystay active during this process.]

Therefore, the MERs (upstream and downstream, if present) may maintainan inactivity timer used to detect potentially stale TEIDs. Theinactivity timer may be preset based on the time it would take for anendpoint (and thus a GTP-U tunnel) to be deemed dormant. In addition,the MERs may use a stale state that checks for TEIDs being assigned toanother user prior to expiration of the inactivity timer. If theinactivity timer has expired or if a TEID has been assigned to anotheruser (stale state is set), then the discovery procedure can be triggeredagain to determine the new TEIDs. In a particular embodiment, thedownstream tunnel may be identified as dormant based on a stale statesetting, for example, due to a GTP-U error indication received from aradio network controller.

Turning to FIG. 7B, FIG. 7B is a simplified block diagram ofcommunication system 10, which (in this particular implementation)includes UE 12 a, RNC 32 e, MER 50 b, SGSN/SGW 34 b, and GGSN/PGW 54 a.In one example, an UE active indicator 96 illustrates that UE 12 a isactive. First upstream tunnel 76 and first downstream tunnel 82 connectRNC 32 e with SGSN/SGW 34 b and second upstream tunnel 78 and seconddownstream tunnel 80 connect SGSN/SGW 34 b with GGSN/PGW 54 a.

In another example, an UE inactive indicator 98 illustrates that UE 12 ais not active and first upstream tunnel 76 and first downstream tunnel82 have been released. Because the tunnels have been released and are nolonger active, MER 50 b is unable to route any data to UE 12 a. If MER50 b does not receive any data from or destined to UE 12 a during thisstate, the issue is not a problem. However, if such traffic is receivedat MER 50 b, then new tunnels should be established for the data toreach UE 12 a. In yet another example, an UE re-active indicator 100illustrates that UE 12 a has been reactivated and a new first upstreamtunnel 86 and a new downstream tunnel 92 have been created.

Using a dormant detection process, where the inactivity timer and thestale state are monitored, MER 50 a is able to determine that firstupstream tunnel 76 and second downstream tunnel 82 have been released,and new first upstream tunnel 86 and new second downstream tunnel 92have been created. If MER 50 a determines that first upstream tunnel 76and second downstream tunnel 82 have been released, MER 50 a can send anin-band message to GGSN/PGW 54 a to obtain the new association/bindingof new first upstream tunnel 86 and new second downstream tunnel 92through the existing tunnels (tunnels 78 and 80). From GGSN/PGW 54 a,MER 50 b is able to determine the TEID for new first upstream tunnel 86and new downstream tunnel 92, and route data to/from the user device.

Turning to FIG. 7C, FIG. 7C is a simplified flowchart 700 illustratingone potential operation associated with the present disclosure. (Notethat FIG. 7C (due to its length) has been broken into two segments:7C-1, 7C-2.) In 702, a MER receives a downstream packet. For example,MER 50 a may receive a downstream packet from default path 60, or frombreakout path 106 that was created when a packet was offloaded. In 704,the MER determines if network address and port translation (NAPT)binding still exists. If NAPT binding does not still exist, then thepacket is dropped, as in 706. If NAPT binding does still exist, then theMER determines if an inactivity timer has expired, as shown in 708. Ifthe inactivity time has expired, then both upstream and downstreamtunnels are marked as stale, as shown in 710 and the packet is buffered(depicted in 714). If the inactivity timer has not expired, then the MERdetermines if the stale state is set, as shown in 712.

If the stale state is not set, then the MER sends the packet to an RNC,as illustrated in 716. In 718, the MER then determines if an errormessage is received from the RNC (indicating that the downstream tunnelTEID is not correct or no longer valid.) If an error message was notreceived, then the MER considers the downstream tunnel TEID to becorrect. If an error message was received, then both upstream anddownstream tunnels are marked as stale, as shown in 710, and the packetis buffered, as depicted in 714. In 720, the MER sends an in-bandmessage to a GGSN/PGW to obtain the identity of the new tunnels. Forexample, MER 50 a may send an in-band message to GGSN/PGW 54 a using GREtunnel 84. In 722, the GGSN/PGW sends in-band message towards a SGSN/SGW34 b using an existing second downstream tunnel, which triggers theSGSN/SGW to start a paging procedure and establish new tunnels to theRNC. For example, GGSN/PGW 54 a may send an in-band message towardsSGSN/SGW 34 b using existing second downstream tunnel 80, which triggersSGSN/SGW 34 b to start a paging procedure and establish new tunnels (86and 92) to RNC 32 e. In 724, the MER receives a MER discovery messagefrom the GGSN that includes the TEID of the new upstream and downstreamtunnels. In 726, using the TEID of the new tunnels, the buffer isdrained and the packet is sent to the RNC.

IP Routing

Turning to FIG. 8A, FIG. 8A is a simplified block diagram ofcommunication system 10, which (in this particular implementation)includes UE 12 a, cell sites 30 a-c, RNC 32, MER 50 a-c, SGSN/SGW 34,GGSN/PGW 54, first upstream tunnel 76, second upstream tunnel 78, firstdownstream tunnel 80, second downstream tunnel 82, out-of-band channel73, GRE tunnel 84, core network 56, and Internet 58. FIG. 8A furtherincludes an IP point of attachment 124.

In accordance with one example implementation, packets from UE 12 a arecommunicated to MER 50 a. Based on instructions from GGSN/PGW 54, MER 50a determines which traffic to offload, where it uses IP-based routing toact as an anchor point. The offloaded traffic 108 is communicated onbreakout path 106. Use of IP-based routing, allows for mid-flow breakoutof traffic and also avoids NAT-ing at MER 50 a. MER 50 a can act as anupstream router instead of incurring the cost of the mobile plane, asthe routing offload point is where the subscriber is hosted and MER 50 aacts as the upstream point to external networks (such as Internet 58).

Data can be routed from its source to its destination through a seriesof routers, and across multiple networks. IP Routing is an umbrella termfor the set of protocols that determine the path that data follows inorder to travel across multiple networks from its source to itsdestination. The IP Routing protocols enable MERs 50 and routers 52 tobuild up a forwarding table that correlates final destinations with nexthop addresses. These protocols can include Border Gateway Protocol(BGP), Intermediate System-Intermediate System (IS-IS), Open ShortestPath First (OSPF), Routing Information Protocol (RIP), etc. When an IPpacket is to be forwarded, a router uses its forwarding table todetermine the next hop for the packet's destination (based on thedestination IP address in the IP packet header), and forwards the packetappropriately. The next router then repeats this process using its ownforwarding table, and so on until the packet reaches its destination. Ateach stage, the IP address in the packet header is sufficientinformation to determine the next hop; no additional protocol headersare required.

In a particular embodiment, MER 50 a assigns IP addresses to eachtraffic flow for which MER 50 a serves as the anchor router. In aparticular embodiment, a range of IP addresses that are the last hop forMER 50 a or GGSN/PGW 54 (which can be configured at differentregularities) are assigned to each traffic flow. In another particularembodiment, IP addresses are dynamically distributed between MER 50 aand GGSN/PGW 54. The assigned IP address allows for traffic to bereturned to either MER 50 a or GGSN/PGW 54.

In a particular embodiment, traffic is de-capsulated at MER 50 a. MER 50a can determine if a de-capsulated packet matches an inner IP accesscontrol list, a TEID, or both. For example, for global ACLconfigurations for PDPs, inner destination IP address is not at theprovider content network (i.e., traffic is toward distributed orInternet content), and for per-PDP ACL, a 5-tuple match for inner IPflow of a PDP context. Further packet analysis on the gateway can beused to determine IP flows of the default bearer, and the secondaryPDP/dedicated bearer is set for breakout. If the packet does match, thenan IP address can be assigned to the packet such that MER 50 a wouldserve as the anchor or host router. If the packet does not match, thenthe packet can be communicated to SGSN/SGW 34.

In accordance with one example implementation, MER 50 a can receivedownstream traffic from Internet 58 and also communicate the traffic toUE 12 a. In another example implementation, MER 50 a receives downstreamtraffic from Internet 58; however, based on the type of traffic,services should be applied to the packet flow and MER 50 a is notnecessarily capable of performing those services. In this case, theoperator serviced traffic 122 that needs the services applied (such astransactions or charging (e.g., Layer 7 billing), firewall capabilities,etc.) can be communicated to GGSN/PGW 54 using GRE tunnel 84. In aparticular embodiment, the operator-serviced traffic 122 cannot beserviced by GGSN/PGW 54 and the operator-serviced traffic 122 isoffloaded to core network 56 for servicing. In this manner, downstreamtraffic is received by MER 50 a and, if further or special services areneeded, operator serviced traffic 122 is communicated from MER 50 a toGGSN/PGW 54 (using GRE tunnel 84 such that the traffic is offloaded tocore network 56). MER 50 a may be capable of performing some servicesdepending on the number of data plane levels available on MER 50 a.

Turning to FIG. 8B, FIG. 8B is a simplified flowchart 800 illustratingone potential operation associated with the present disclosure. In 802,traffic is received at a MER. For example, upstream or downstreamtraffic may be received at MER 50 a. In 804, the MER can determine ifthe traffic is GTP-U encapsulated. If the traffic is not GTP-Uencapsulated, then the MER can determine if the traffic is mobiletraffic, at 806. If the traffic is not mobile traffic, then standardrouting functions are performed, at 808. If the traffic is mobiletraffic, then the functions as specified by a MER-CA are performed onthe traffic, at 810. If the traffic is GTP-U encapsulated, then the MERcan determine if the traffic is upstream traffic or downstream traffic,at 812.

If the traffic is downstream traffic, the MER can determine if it isexpecting to receive traffic from the GGSN on the TEID and inner IP, at814. If traffic is not expected from the GGSN on the TEID and inner IP,then the TEID is marked as stale and rediscovery is initiated, at 816.If the MER is expecting to receive traffic from the GGSN on the TEID andinner IP, then the packet is communicated to a RNC or an eNode B by theMER, at 818.

If the traffic is upstream traffic, then the MER de-capsulates thepacket, and can determine if the de-capsulated packet matches an innerIP access control list, a TEID, or both, as shown in 820. If the MERdetermines that the de-capsulated packet does match an inner IP accesscontrol list, a TEID, or both, then an IP address is assigned to thede-capsulated packet and the de-capsulated packet is broken out, asshown in 822. If the MER determines that the de-capsulated packet doesnot match an inner IP access control list, a TEID, or both, then thede-capsulated packet is communicated on to a GGSN, as shown in 824. Forexample, using GRE tunnel 84, MER 50 a may communicate to GGSN/PGW 34, ade-capsulated packet that needs a service performed.

Turning to FIG. 8C, FIG. 8C is a simplified block diagram ofcommunication system 10, which (in this particular implementation)includes UE 12 a, cell sites 30 a-c, RNC 32, MER 50 a-c, SGSN/SGW 34,GGSN/PGW 54, first upstream tunnel 76, second upstream tunnel 78, firstdownstream tunnel 80, second downstream tunnel 82, out-of-band channel73, GRE tunnel 84, core network 56, and Internet 58. FIG. 8C may alsoinclude an embedded NAT 110. FIG. 8C is similar to FIG. 8A except forthe addition of embedded NAT 110. When a packet in the traffic flowneeds extra processing outside GGSN/PGW 54 (CDR generation, complexCDRS, voice) and those packets still have the source IP addressoriginally assigned by MER 50 a. The addition of embedded NAT 110 canhelp facilitate the extra processing and ensure the traffic is returnedto GGSN/PGW 54.

NAT-ing is the process of modifying IP address information in the IPpacket header of the packet in the traffic flow, while the packet is intransit across MER 50 a. The simplest type of NAT provides a one-to-onetranslation of IP addresses (e.g., basic NAT or one-to-one NAT). In thistype of NAT, the IP addresses, IP header checksum, and/or anyhigher-level checksums (that include the IP address) are changed. Therest of the packet can be left untouched (at least for basic TCP/UDPfunctionality, some higher-level protocols may need furthertranslation).

Basic NATs can be used when there is a requirement to interconnect twoIP networks with incompatible addressing. However, it is common to hidean entire IP address space, usually consisting of private IP addresses,behind a single IP address (or in some cases a small group of IPaddresses) in another (usually public) address space. To avoid ambiguityin the handling of returned packets, a one-to-many NAT should alterhigher-level information such as TCP/UDP ports in outgoingcommunications and, further, should maintain a translation table so thatreturn packets can be correctly translated back. (e.g., NAPT or portaddress translation (PAT), IP masquerading, NAT Overload, etc.).

In accordance with one example implementation described in FIG. 8A,downstream traffic ended up at MER 50 a and MER 50 a determined whetheror not the traffic could be communicated to UE 12 a, or if the trafficneeded to shift to GGSN/PGW 54 for services. When flows are not beingoffloaded (or flow through the GRE tunnel), and have services applied,in order to return the downstream packets for a user (for a non-brokenout flow) NAT 110 assigns the user a different IP address. For example,some complex services can be applied at GGSN/PGW 54 using core network56.

The upstream traffic with the complex services is communicated toGGSN/PGW 54 and is NAT-ed before it is communicated to core network 56so the traffic will return to GGSN/PGW 54. Otherwise, the traffic can beoffloaded, FIG. 8A, and the source address of the upstream is still theone that was assigned to the user. If the traffic is not uploaded, itstill has the source address of the user. Hence, NAT 110 assigns adifferent IP address before the traffic is sent to core network 56. Thatnew source address allows the packet to return back to the GGSN/PGW 54and not MER 50 a.

Turning to FIG. 8D, FIG. 8D is a simplified flowchart 801 illustratingone potential operation associated with the present disclosure. In 822,upstream traffic is received at a MER and is de-capsulated. The MERdetermines if a de-capsulated packet matches an inner IP access controllist, a TEID, or both, as in 824. If the MER determines that thede-capsulated packet matches an inner IP access control list, a TEID, orboth, then an IP address is assigned to the de-capsulated packet and thede-capsulated packet is broken out, as in 826. If the MER determinesthat the de-capsulated packet does not match an inner IP access controllist, a TEID, or both, then the de-capsulated packet is communicated onto an SGSN/SGW, as in 828. In 830, the GGSN/PGW determines if a serviceshould be performed on the de-capsulated packet that cannot be performedby the GGSN/PGW. If the GGSN/PGW determines that the service cannot beperformed by the GGSN/PGW, then NAT binding is attached to thede-capsulated packet and the de-capsulated packed is sent forprocessing, as in 834. If the GGSN/PGW determines that the service canbe performed by the GGSN/PGW, then the GGSN/PGW can perform the serviceon the de-capsulated packet, as in 832.

NAT Routing

Turning to FIG. 9A, FIG. 9A is a simplified block diagram ofcommunication system 10, which (in this particular implementation)includes UE 12 a, cell sites 30 a-c, RNC 32, MER 50 a, routers 52,SGSN/SGW 34, GGSN/PGW 54, first upstream tunnel 76, second upstreamtunnel 78, first downstream tunnel 80, second downstream tunnel 82,out-of-band channel 73, GRE tunnel 84, core network 56, embedded NAT110, IP point of attachment 124, and Internet 58.

In accordance with one example implementation, packets from UE 12 a arecommunicated to MER 50 a. MER 50 a determines which traffic to offloadand uses embedded NAT 110 to act as an anchor point. Use of NAT allowsfor a mid-flow breakout of traffic and does not require MER 50 a to bean anchor point. For example, if UE 12 a is mobile, MER may be moved toa new MER and the new MER could become the new anchor MER. MER 50 a actsas the upstream point of attach to external networks (such as Internet58). When the anchor point moves to the new MER, the IP session may bekept. In a particular embodiment, a tunnel is established between theanchor MER and the new MER to provide a mobile support.

In a particular embodiment, traffic is de-capsulated at MER 50 a. MER 50a determines if a de-capsulated packet matches an inner IP accesscontrol list, a TEID, or both. (For example, if global configurationsACL for PDPs: inner destination IP address is not at provider contentnetwork (i.e., traffic is toward distributed or Internet content),per-PDP ACL: 5-tuple match for inner IP flow of a PDP context. DPI on GWis used to determine IP flows of PDP context, and entire secondaryPDP/dedicated bearer is set for breakout.) If the packet does match,then the inner IP of the packet is NAT-ed such that MER 50 a will be theanchor router. If the packet does not match, then the packet iscommunicated to SGSN/SGW 34. Because the packet is NAT-ed, the anchorpoint for the offloaded packet is MER 50 a. MER 50 a receives theoffloaded packet as downstream traffic from Internet 58 and communicatesthe packet to UE 12 a. In a particular embodiment, MER 50 a determinesif services should be applied to the offloaded packet. If services arenecessary, then the offloaded packet may be NAT-ed such that theoffloaded packet will return to GGSN/PGW 54 where the services can beapplied. Hence, the packet would not be returned to MER 50 a and thentunneled back to GGSN/PGW 54, the packet would go directly to GGSN/PGW54.

Turning to FIG. 9B, FIG. 9B is a simplified flowchart 900 illustratingone potential operation associated with the present disclosure. In 902,traffic is received at a MER. In 904, the MER determines if the trafficis upstream traffic or downstream traffic. If the traffic is downstreamtraffic, based on the NAT binding of the downstream traffic, the GTPtunnel header and TEID are restored by the MER and the MER can performany general packet radio service tunneling protocol sequencing, as in906. In 908, the downstream traffic is communicated to a RNC.

If the traffic is upstream traffic, the MER determines if a packetmatches an inner IP access control list, a TEID, or both, as in 910. Ifthe MER determines that the packet does not match, then the packet iscommunicated on to an SGSN/SGW, as in 912. For example, if MER 50 adetermines that the packet does not match, then the packet iscommunicated on to an SGSN/SGW 34. If the MER determines that the packetdoes match, then the packet is de-capsulated and the de-capsulatedpacket is NAT-ed and broken out, as shown in 914.

Turning to FIG. 9C, FIG. 9C is a simplified block diagram ofcommunication system 10, which (in this particular implementation)includes UE 12 a, cell sites 30 a-c, RNC 32, MER 50 a, routers 52,SGSN/SGW 34, GGSN/PGW 54, first upstream tunnel 76, second upstreamtunnel 78, first downstream tunnel 80, second downstream tunnel 82,out-of-band channel 73, GRE tunnel 84, core network 56, carrier gradeNAT (CGN) 112, IP point of attachment 124, and Internet 58. Inaccordance with one example implementation, packets from UE 12 a arecommunicated to MER 50 a. MER 50 a determines which traffic to offloadand uses carrier grade NAT (CGN) 112 to act as an anchor point.

CGN (sometimes referred to as large-scale NAT (LSN)), is an approach toIPv4 network design where end sites (for example homes) are not givenpublic IPv4 addresses. Instead, the end sites are given privateaddresses that are translated to public by middleboxes embedded in anetwork operator's network. This allows the network operator to share acommon pool or pools of addresses among several end sites. CGN can alsobe used for IPv6 as well as translation between IPv4 and IPv6.

Asymmetric Routing

Turning to FIG. 10A, FIG. 10A is a simplified block diagram of a portionof communication system 10 depicting one example of an asymmetricrouting 102 a. Asymmetric routing 102 a can include RNC 32, MER 50 a,MER 50 b, and SGSN/SGW 34. In this example, link 126 connects RNC 32with MER 50 a, link 128 connects RNC 32 with MER 50 b, link 130 connectsMER 50 a with SGSN/SGW 34, and link 132 connects MER 50 b with SGSN/SGW34.

In some deployments, routers or MERs may be configured to operate in anactive/active mode instead of active/standby mode. For example, MER 50 aand MER 50 b may be configured to operate in an active/active mode whereboth are active. In this case, UE's traffic may be loadbalanced betweenMER 50 a and MER 50 b without UE's awareness. As a result, traffic fromone UE may traverse through different routers (or MERs) and the controlof such traffic becomes more challenging. In one particular embodiment,policy based routing (PBR) may be used to bring mobile-related trafficto one MER for service enforcement. The service enforcement is inactive/standby mode while the routers are in active/active mode. Inanother particular embodiment, a new function to MER is added such thatthe service enforcement forwards mobile traffic of specific subscribersto peers responsible for the control of such subscribers.

FIG. 10B is a simplified schematic diagram illustrating possibleexamples of a link (e.g., link 126 or link 130) to MER 50 a becomingdisabled. For example, 102 b depicts link 126 becoming disabled (e.g.,due to a loss of connection between RNC 32 and MER 50 a). In aparticular embodiment, PBR is used to reroute traffic 104 a (that wascommunicated from MER 50 a to RNC 32 over link 126) from MER 50 b to RNC32 (over link 128). Because link 130 is still active and not disabled,traffic 104 c continues to flow from/to MER 50 a to/from SGSN/SGW 34over link 130.

In a similar example, 102 c depicts link 130 becoming disabled (e.g.,due to a loss of connection between MER 50 a and SGSN/SGW 34). In aparticular embodiment, PBR is used to reroute traffic 104 c (that wascommunicated from MER 50 a to SGSN/SGW 34 over link 130) from MER 50 bto SGSN/SGW 34 over link 132. Because link 126 is still active and notdisabled, traffic 104 a continues to flow from/to MER 50 a to/from RNC32 over link 126.

FIG. 10C is a simplified schematic diagram illustrating possibleexamples of a link (e.g., link 128 or link 132) to MER 50 b becomingdisabled. For example, 102 d depicts link 128 becoming disabled (e.g.,due to a loss of connection between RNC 32 and MER 50 b). In aparticular embodiment, PBR is used to reroute traffic 104 b (that wascommunicated from MER 50 b to RNC 32 over link 128) from MER 50 a to RNC32 (over link 126). Because link 132 is still active and not disabled,traffic 104 d continues to flow from/to MER 50 b to/from SGSN/SGW 34over link 132.

In a similar example, 102 e depicts link 132 becoming disabled (e.g.,due to a loss of connection between MER 50 b and SGSN/SGW 34). In aparticular embodiment, PBR is used to reroute traffic 104 d (that wascommunicated from MER 50 b to SGSN/SGW 34 over link 132) from MER 50 ato SGSN/SGW 34 over link 130. Because link 128 is still active and notdisabled, traffic 104 b continues to flow from/to MER 50 b to/from RNC32 over link 128.

FIG. 10D is a simplified schematic diagram illustrating two possibleexamples of a MER (e.g., MER 50 a or MER 50 b) becoming disabled. Forexample, 102 f depicts MER 50 b becoming disabled (e.g., due to amechanical failure of MER 50 b). In a particular embodiment, PBR can beused to reroute traffic 104 b that was communicated from MER 50 b to RNC32 over link 128, and to reroute traffic 104 d that was communicatedfrom MER 50 b to SGSN/SGW 34 over link 132. Because links 126 and 130are still active and not disabled, traffic can be communicated from MER50 a to RNC 32 over link 126, and to SGSN/SGW 34 over link 130.

In a similar example, 102 g illustrates a scenario in which MER 50 a hasbecome disabled (e.g., due to a mechanical failure of MER 50 a). In aparticular embodiment, PBR can be used to reroute traffic 104 a that wascommunicated from MER 50 a to RNC 32 over link 126, and reroute traffic104 c that was communicated from MER 50 b to SGSN/SGW 34 over link 130.Because links 128 and 132 are still active and not disabled, traffic canbe communicated from MER 50 b to RNC 32 over link 128, and to SGSN/SGW34 over link 132.

FIG. 10E is a simplified schematic diagram illustrating an example ofwhen link 130 has become disabled (e.g., due to a loss of connectionbetween MER 50 a and SGSN/SGW 34) and the link failure does not triggera MER switchover. As shown in the example, traffic 104 a, 104 b, 104 c,and 104 d should first propagate through MER 50 a and then be reroutedthrough MER 50 b. As a result, inter-chassis traffic becomes extreme(i.e., may require additional physical links to be installed on bothrouters).

FIG. 10F is a simplified schematic diagram illustrating a graphicalexample of when link 130 has become disabled (e.g., due to a loss ofconnection between MER 50 a and SGSN/SGW 34), and the link failuretriggers a MER switchover. As shown in the example, traffic 104 b, 104c, and 104 d does not first propagate through MER 50 a and then bererouted through MER 50 b. Instead, traffic 104 a is routed from MER 50b to MER 50 a. As a result, inter-chassis traffic does not becomesextreme (i.e., does not require additional physical links to beinstalled on both routers). In order to achieve the re-routing oftraffic, certain link failures may trigger MER switchover based onconfigured policies and available inter-chassis bandwidth

Turning to FIG. 11, FIG. 11 is a simplified block diagram of an in-bandsignaling packet 134. In-band signaling packet 134 may include an outertunnel IP header 136, an inner packet IP header 138, and a payload 140.Fields 102 and fields 142 (or a subset) indicate parameters that can beconfigured by MER 50 a and/or a MER-CA (e.g., GGSN/PGW 54). Fields 144(or a subset) indicate parameters that should be used withoutmodifications.

Payload 140 may contain in-band protocol data elements. For example,payload 140 may contain the type of message, the IP assigned to UE(e.g., UE 12 a), downstream and upstream TEIDs, packet hashes, MER CAand MER Control Plane/Data Plane (CP/DP) address/port to be used, MERand MER CA ID, and future extensions, which can include other elements.The message type may be a MER discovery message, a TEIDdiscovery/loopback, an end-marker, a paging trigger, or futureextensions.

Note that in certain example implementations, the data communication androuting functions outlined herein may be implemented by logic encoded inone or more tangible media (e.g., embedded logic provided in anapplication specific integrated circuit [ASIC], network processors,digital signal processor [DSP] instructions, software [potentiallyinclusive of object code and source code] to be executed by a processor,or other similar machine, etc.). In some of these instances, a memoryelement [as shown in FIG. 3A] can store data used for the operationsdescribed herein. This includes the memory element being able to storesoftware, logic, code, or processor instructions that are executed tocarry out the activities described in this Specification.

A processor can execute any type of instructions associated with thedata to achieve the operations detailed herein in this Specification. Inone example, the processor [as shown in FIG. 3A] could transform anelement or an article (e.g., data) from one state or thing to anotherstate or thing. In another example, the data communication and routingactivities outlined herein may be implemented with fixed logic orprogrammable logic (e.g., software/computer instructions executed by aprocessor) and the elements identified herein could be some type of aprogrammable processor, programmable digital logic (e.g., a fieldprogrammable gate array [FPGA], an erasable programmable read onlymemory (EPROM), an electrically erasable programmable ROM (EEPROM)) oran ASIC that includes digital logic, software, code, electronicinstructions, or any suitable combination thereof.

In one example implementation, MER 50 a and/or MER-CA (e.g., GGSN/PGW54) may include software (e.g., provisioned as traffic offload module66, MER control module 74, etc.) in order to achieve the datacommunication functions outlined herein. These devices may further keepinformation in any suitable memory element [random access memory (RAM),ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any othersuitable component, device, element, or object where appropriate andbased on particular needs. Any of the memory items discussed herein(e.g., database, tables, trees, queues, caches, etc.) should beconstrued as being encompassed within the broad term ‘memory element.’Similarly, any of the potential processing elements, modules, andmachines described in this Specification should be construed as beingencompassed within the broad term ‘processor.’ Each of these elements(e.g., MER 50 a and MER-CA (e.g., GGSN/PGW 54)) can also includesuitable interfaces for receiving, transmitting, and/or otherwisecommunicating data or information in a network environment.

MER 50 a and MER-CA (e.g., GGSN/PGW 54) are network elements configuredto perform the traffic offloading activities disclosed herein. As usedherein in this Specification, the term ‘network element’ may include anysuitable hardware, software, components, modules, interfaces, or objectsoperable to exchange information in a network environment. Further, theterm network element as discussed herein encompasses (but is not limitedto) devices such as routers, switches, gateways, bridges, loadbalancers,firewalls, inline service nodes, proxies, clients, servers processors,modules, or any other suitable device, component, element, proprietarydevice, network appliance, or object operable to exchange information ina network environment. This may be inclusive of appropriate algorithmsand communication protocols that allow for the effective exchange ofdata or information.

Note that with the example provided above, as well as numerous otherexamples provided herein, interaction may be described in terms of two,three, or four network elements. However, this has been done forpurposes of clarity and example only. In certain cases, it may be easierto describe one or more of the functionalities of a given set of flowsby only referencing a limited number of network elements. It should beappreciated that communication system 10 (and its teachings) are readilyscalable and can accommodate a large number of components, as well asmore complicated/sophisticated arrangements and configurations.Accordingly, the examples provided should not limit the scope or inhibitthe broad teachings of communication system 10 as potentially applied toa myriad of other architectures.

It is also important to note that the steps in the preceding flowdiagrams illustrate only some of the possible scenarios and patternsthat may be executed by, or within, communication system 10. Some ofthese steps may be deleted or removed where appropriate, or these stepsmay be modified or changed considerably without departing from the scopeof the present disclosure. In addition, a number of these operations mayhave been described as being executed concurrently with, or in parallelto, one or more additional operations. However, the timing of theseoperations may be altered considerably. The preceding operational flowshave been offered for purposes of example and discussion. Substantialflexibility is provided by communication system 10 in that any suitablearrangements, chronologies, configurations, and timing mechanisms may beprovided without departing from the teachings of the present disclosure.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. It is also imperative to notethat the architecture outlined herein can be used in different types ofnetwork applications. The architecture of the present disclosure canreadily be used such environments, as the teachings of the presentdisclosure are equally applicable to all such alternatives andpermutations.

In order to assist the United States Patent and Trademark Office (USPTO)and, additionally, any readers of any patent issued on this applicationin interpreting the claims appended hereto, Applicant wishes to notethat the Applicant: (a) does not intend any of the appended claims toinvoke paragraph six (6) of 35 U.S.C. section 112 as it exists on thedate of the filing hereof unless the words “means for” or “step for” arespecifically used in the particular claims; and (b) does not intend, byany statement in the specification, to limit this disclosure in any waythat is not otherwise reflected in the appended claims.

1. A method, comprising: receiving a data packet transported on abackhaul link at a first network element; de-capsulating the datapacket; identifying whether the data packet is an upstream data packet;identifying whether the data packet matches an internet protocol (IP)access control list (ACL) or a tunnel endpoint identifier; andoffloading the data packet from the backhaul link.
 2. The method ofclaim 1, further comprising: identifying that the data packet does notmatch the IP ACL or the tunnel endpoint identifier; and communicatingthe data packet to a second network element.
 3. The method of claim 1,further comprising: identifying that the data packet is a downstreamdata packet; identifying a service to be performed for the data packetthat cannot be performed at the first network element; and communicatingthe data packet to a second network element.
 4. The method of claim 1,further comprising: assigning an IP address to the data packet; andperforming a network address translation on the data packet at a gatewaygeneral packet radio service support node.
 5. The method of claim 1,further comprising: identifying that the data packet is a downstreamdata packet; and restoring a tunnel header and tunnel identificationbased on an IP address of the data packet.
 6. The method of claim 1,further comprising: performing a general packet radio service tunnelingprotocol sequencing.
 7. The method of claim 1, further comprising:identifying that the data packet is a downstream data packet; andcommunicating the data packet to a radio network controller or an eNodeB.
 8. Logic encoded in one or more non-transitory media that includescode for execution and when executed by a processor is operable toperform operations comprising: receiving a data packet transported on abackhaul link at a first network element; de-capsulating the datapacket; identifying whether the data packet is an upstream data packet;identifying whether the data packet matches an internet protocol (IP)access control list (ACL) or a tunnel endpoint identifier; andoffloading the data packet from the backhaul link.
 9. The logic of claim8, the operations further comprising: identifying that the data packetdoes not match the IP ACL or the tunnel endpoint identifier; andcommunicating the data packet to a second network element.
 10. The logicof claim 8, the operations further comprising: identifying that the datapacket is a downstream data packet; identifying a service to beperformed for the data packet that cannot be performed at the firstnetwork element; and communicating the data packet to a second networkelement.
 11. The logic of claim 8, the operations further comprising:assigning an IP address to the data packet; and performing a networkaddress translation on the data packet at a gateway general packet radioservice support node.
 12. The logic of claim 8, the operations furthercomprising: identifying that the data packet is a downstream datapacket; and restoring a tunnel header and tunnel identification based onan IP address of the data packet.
 13. The logic of claim 8, theoperations further comprising: performing a general packet radio servicetunneling protocol sequencing.
 14. The logic of claim 8, the operationsfurther comprising: identifying that the data packet is a downstreamdata packet; and communicating the data packet to a radio networkcontroller or an eNode B.
 15. An apparatus, comprising: a memory elementconfigured to store data; a processor operable to execute instructionsassociated with the data; a traffic offload module configured tointerface with the memory element and the processor, wherein theapparatus is configured for: receiving a data packet transported on abackhaul link at a first network element; de-capsulating the datapacket; identifying whether the data packet is an upstream data packet;identifying whether the data packet matches an internet protocol (IP)access control list (ACL) or a tunnel endpoint identifier; andoffloading the data packet from the backhaul link.
 16. The apparatus ofclaim 15, the apparatus further configured for: identifying that thedata packet does not match the IP ACL or the tunnel endpoint identifier;and communicating the data packet to a second network element.
 17. Theapparatus of claim 15, the apparatus further configured for: identifyingthat the data packet is a downstream data packet; identifying a serviceto be performed for the data packet that cannot be performed at thefirst network element; and communicating the data packet to a secondnetwork element.
 18. The apparatus of claim 15, the apparatus furtherconfigured for: assigning an IP address to the data packet; andperforming a network address translation on the data packet at a gatewaygeneral packet radio service support node.
 19. The apparatus of claim15, the apparatus further configured for: identifying that the datapacket is a downstream data packet; and restoring a tunnel header andtunnel identification based on an IP address of the data packet.
 20. Theapparatus of claim 15, the apparatus further configured for: performinga general packet radio service tunneling protocol sequencing.